Adaptive content platform and method of using same

ABSTRACT

An adaptive content platform includes one or more content-enabled, dependent applications, each of which includes a user interface and business logic. A services layer, which is interfaced with the dependent applications and a software infrastructure, provides one or more services that are usable by the dependent applications.

RELATED APPLICATIONS

This application claims the priority of: U.S. Provisional PatentApplication No. 60/394,441, entitled “Adaptive Content Platform”, andfiled on Jul. 9, 2002.

BACKGROUND

This invention relates to software development, and more particularly tosoftware development platforms.

For a suite of applications developed for a common software platform(e.g., an application server platform), each application within thesuite typically includes a group of services (e.g., content managementservices, workflow services, publishing services, search and queryservices) that are common amongst the applications in the suite.

As the software platform does not allow the services of one applicationto be shared by another, these services must be coded for and includedin each application written for the software platform, even thoughmultiple applications use common services.

SUMMARY

According to an aspect of this invention, an adaptive content platformincludes one or more content-enabled, dependent applications (thusforming an application layer), each of which includes a user interfaceand business logic. A services layer, which is interfaced with thecontent-enabled dependent applications and a software infrastructure(e.g., an application server), provides one or more services that areusable by the content-enabled, dependent applications.

One or more of the following features may be included. The serviceslayer includes a unique application programming interface for each ofthe one or more services, such that dependent applications using aspecific service make requests through the application programminginterface assigned to that service.

The services include a content management service (for storing andmanaging files), which includes: a repository service for storing files;and a search service for allowing users to search files stored by therepository service, for example.

The services also include a workflow and collaboration service (formanaging projects and users), which includes: a workflow service formanaging the workflow of files; a user management and authenticationservice for managing the users and user groups; and an events andnotification service for managing and broadcasting notifications to theusers that were generated by the services, for example.

Additionally, the services include a multi-modal content creationservice (for manual creation and automated importation and conversion offiles), which includes: a transformation and content handling servicefor converting the formats of files; a desktop integration service formanual contribution of content; and an import service for facilitatingfile importation from external systems, for example.

The services further include a multi-channel deployment service (forpublishing files to one or more publishing channels), which includes: apublishing service for publishing files to one or more publishingchannels (such as a web site, an email broadcast, a wireless broadcast,a syndication stream, or a printed publication, for example); a dynamicpublishing service; and a static publishing service, for example.

A data layer is interfaced with the software infrastructure, such thatthe data layer includes one or more databases.

The above-described adaptive content platform may be implemented in adistributed computing system, in that a first (or local) computingdevice executes the content-enabled, dependent applications, and asecond (or remote) computing device executes the services layer. Thissecond computer may be a web server.

In a distributed computing system, the first and second computingdevices are interconnected by a network, such as a local area network,the Internet, or an intranet, for example.

The above-described adaptive content platform and distributed computingsystem may be implemented as a method or a sequence of instructionsexecuted by a processor.

One or more advantages can be provided from the above. By providing theprogrammer with a common set of reusable services, applications are nolonger required to include stand-alone services. Since theseapplications are not required to include services, applicationdevelopment is significantly accelerated and deployment is simplified.Additionally, by using a common set of services, compatibility issuesare minimized. Further, as applications share a common set of services,application size is reduced. In addition, by separating an application'sservices from the application's business logic/user interface,distributed computing is possible, leading to superior scalability andavailability.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the invention will be apparent from thedescription and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an adaptive content platform;

FIG. 2 is a block diagram of a content management group of the adaptivecontent platform;

FIG. 3 is a block diagram of a workflow and collaboration group of theadaptive content platform;

FIG. 4 is a block diagram of a multi-modal content creation group of theadaptive content platform;

FIG. 5 is a block diagram of a multi-channel deployment group of theadaptive content platform;

FIG. 6 is a block diagram the adaptive content platform incorporatedinto a distributed computing system;

FIG. 7 is a flow chart of a distributed computing method; and

FIG. 8 is a flow chart of a multi-tier software development method.

DETAILED DESCRIPTION

Referring to FIG. 1, an adaptive content platform 10 includes one ormore dependent applications 12, 14, 16, each of which includes a userinterface (e.g., user interface 18) and business logic (e.g., businesslogic 20). This group of dependent applications may be referred to as anapplication layer 22. Each user interface 18 allows a user of thedependent application to access and use the functionality of thedependent application. Business logic 20 performs the functions nativeto the dependent application. Note that while dependent applicationstypically include some form of user interface, this is not required.

Typically, the dependent applications 12, 14, 16, are content-enableddependent applications, in that they manage and process content (e.g.,documents, images, audio clips, video clips). Examples ofcontent-enabled applications are web content management systems,shareholder and regulatory reporting applications, corporate marketingand communications systems, newspaper publishing systems, and so forth.Content-enabled applications typically include a combination of contentmanagement, workflow management, and publishing capabilities.

Adaptive content platform 10 is a multi-tiered software architecturethat includes a services layer 24 for interfacing the application layer22 and a software infrastructure 26 (e.g., an application server).Examples of an application server are BEA Weblogic™, and IBM Websphere™,both of which implement the Java™ 2 Enterprise Edition standard (J2EE).

Services layer 24 provides a group of services 28, 30, 32, which areavailable for use by dependent applications 12, 14, 16. Examples ofthese services include content management services, search services, andfile conversion services, for example. These services, which will bediscussed below in greater detail, are shared services common to thedependent applications; as opposed to each dependent application'snative functions, which are handled by the dependent application'sbusiness logic.

Dependent applications 12, 14, 16 maybe J2EE (“Java™ 2 EnterpriseEdition”) compliant dependent applications that adhere to v1.3 standardsand are compatible with and run on a Java™ 2 Enterprise Editionapplication server.

A data layer 34 is interfaced to the software infrastructure 26, andprovides data services for platform 10. Data layer 34 may provide accessto database servers 36, such as Oracle™, IBM DB2™, and Microsoft SQLServer™. Further, data layer 34 may provide access to file servers 38,such as Microsoft Windows 2000 Servers™, Microsoft Windows NT Servers™,and Unix Servers™. Additionally, data layer 34 may allow access tolegacy systems 40 (i.e., applications and data that have been inheritedfrom languages, platforms, and techniques earlier than currenttechnology).

Data layer 34 is typically interfaced with an operating system (OS)layer 42, which includes the operating system that manages theabove-described layers, infrastructures, and dependent applications.Examples of compatible operating systems are Windows™, Solaris™, andLinux™.

Typically, a web server layer 44 is interfaced with the applicationlayer (i.e., dependent applications 12, 14, 16) and allows a user (notshown) to use and access the functionality of the individual dependentapplications from with a web browser 46 (e.g., Microsoft InternetExplorer™, Netscape Navigator™). Examples of web server layer 44 areMicrosoft Internet Information Server™, and Apache web server™.

By combining the user interface 18 and business logic 20 of a dependentapplication 12 with one or more of the services 28, 30, 32 offered bythe services layer 24, the functionality of a “stand-alone” independentapplication 48 can be emulated without the application having to includededicated services 50, 52, 54.

Concerning the services 28, 30, 32, offered by services layer 24, theseservices can typically be loosely described as four groups of services,namely: content management; workflow and collaboration; multi-modalcontent creation; and multi-channel deployment, each of which will bediscussed below in greater detail.

Referring to FIG. 2, the content management group 100, which stores andmanages files and content used by the adaptive content platform, mayinclude a repository service 102 and a search service 104.

Repository service 102 works in conjunction with the data layer(generally), and the database servers, the file servers, and the legacysystems (specifically) to store, organize, and manage files and content(hereinafter “files”).

Repository service 102 allows for the production, organization, andmanagement of numerous content types that define the specific type offiles being produced and managed. Additionally, repository service 102allows users/administrators to define numerous property fields ormeta-data fields (e.g., release date, revision number, production date,revision date, and approval date, for example) that define and refinethe files stored by the data layer. Access to the files managed byrepository service 102 can be controlled by regulating the users who canview, check out, edit, print, and save a particular file, for example.Additionally, the data structure in which the files are stored (e.g.,the directory tree structure) is defined and controlled using repositoryservice 102. Typically, repository service 102 works in conjunction witha relational database, e.g., database 36 (FIG. 1), that is accessedthrough data layer 34 (FIG. 1).

The search service 104 allows a user to search the files stored by therepository service 102. Searches may be performed on either fileproperties or content. If the files are stored in a structured database(as described above), search service 104 may be an SQL (“structuredquery language”) database query engine. Alternatively, if the files arestored as HTML or XML (“Extensible Markup Language”) based documents,search service 104 may use search engine technology to generate a listof relevant documents.

The dependent applications 12, 14, 16 (FIG. 1) described above mayaccess each service offered by content management group 100 (e.g.,repository service 102 and search service 104) by making the appropriaterequest of and establishing a connection through the API (“applicationprogramming interface”) assigned to that particular service. Forexample, API 106 is assigned to repository service 102, and API 108 isassigned to search service 104. Therefore, if a user of a dependentapplication (e.g., dependent application 12, FIG. 1) wanted to execute asearch for a particular file, dependent application 12 would make theappropriate request from API 108.

Referring to FIG. 3, the workflow and collaboration group 150, whichmanages projects and users of the adaptive content platform, may includea workflow service 152, a user management and authentication service154, and an events and notification service 156.

The workflow service 152 allows the administrator or user to control theworkflow of files through the adaptive content platform. For example, ifa file is produced for publishing purposes, that file might need to beapproved by a midlevel manager prior to it being sent to an upper levelmanager. Further, the upper level manager might have to approve the fileprior to it being published or otherwise disseminated. Therefore,workflow service 152 could mandate that the file be approved by amidlevel manager prior to it being sent to the higher level manager, whoapproves it prior to publication. Further, workflow service 152 mayassign time limits for the completion of certain tasks, such as themidlevel or upper level review and approval process.

The user management and authentication service 154 provides a set oftools to the user/administrator that allows them to manage users anduser groups. Individual users can be produced and deleted using usermanagement and authentication service 154. Further, the rights andprivileges of these individual users also can be controlled andregulated. Additionally, these users can be assigned to, moved between,and deleted from various users groups, which are also maintained usinguser management and authentication service 154. Further, as rights andprivileges can be assigned to a user group, by adding an individual userto a user group, the rights or privileges of an individual user can beefficiently defined.

The events and notification service 156 allows for the delivery ofnotification events generated by the services offered by the appletservice layer 24 (FIG. 1). These message can be delivered to individualusers of the system, broadcast to entire user groups, or delivered tothe various services offered by the applet service layer 24 (FIG. 1).

As above, the dependent applications 12, 14, 16 (FIG. 1) described abovemay access each service offered by workflow and collaboration group 150(e.g., workflow service 152, user management and authentication service154, and the events and notification service 156) by making theappropriate request of and establishing a connection through the APIassigned to that particular service. For this particular group, API 158is assigned to the workflow service 152, API 160 is assigned to the usermanagement and authentication service 154, and API 162 is assigned tothe events and notification service 156.

Referring to FIG. 4, the multi-modal content creation group 200, whichimports and converts files for the adaptive content platform, mayinclude a transformation and content handling service 202, an importservice 204, and a desktop integration service 210.

The transformation and content handling service 202 provides file formatconversion services, thus allowing the user to import files of varioustypes and convert them over into a common format (e.g., XML and HTML).Converter templates are available for popular applications, such asMicrosoft Word™, Microsoft Excel™, Adobe PDF™, and MicrosoftPowerPoint™, for example.

The import service 204 allows for automated import of files fromexternal systems. Import service 204 is configured to monitor, on aperiodic basis, the files located on a network drive, an FTP (“filetransfer protocol”) site, and an HTTP site. When new files are detectedon one of these sources, the files are automatically imported into thesystem. Further, if a format conversion is required, import service 204will work in conjunction with transformation service 202 to import andconvert the file.

The desktop integration service 210 allows content to be contributed byusers via standard desktop creation tools. These tools include theMicrosoft Office™ suite, as well as Adobe™ and Macromedia™ applications.The service uses the WEBDAV protocol (WEB-based Distributed Authoringand Versioning), which is an extension of the HTTP protocol, tocommunicate with the desktop tools.

As above, the dependent applications 12, 14, 16 (FIG. 1) described abovemay access each service offered by multi-modal content creation group200 (e.g., transformation service 202, import service 204, and desktopintegration service 210) by making the appropriate request of andestablishing a connection through the API assigned to that particularservice. For this particular group, API 206 is assigned to thetransformation service 202, API 208 is assigned to the import service204, and API 212 is assigned to the desktop integration service 210.

Referring to FIG. 5, the multi-channel deployment group 250, whichpublishes files to one or more publishing channels, may include a staticpublishing service 252, and a dynamic publishing service 254.

The static publishing service 252 allows for proactive publishing offiles based on predefined templates. Therefore, the structure and formatof the file published (and the document produced) is defined ahead oftime and is not varied depending on the content of the document.Additionally, the content itself is semi-dynamic, in that it changesperiodically (e.g. a few times a week). An example of static documentsgenerated using a static publishing service is a newsroom home page of acorporate web site in which one hundred press releases are currentlybeing displayed. The home page is a collection of one hundred summarylinks, and each link leads to a press release detail page. A corporatecommunications officer can publish the home page and the one hundreddetail pages by invoking the static publishing service, which merges theappropriate press release content with the detail page template togenerate HTML. By generating the pages using static publishing, thecommunications officer ensures that web site visitors have fast pageretrieval, since the content is already in HTML format and does not needto be regenerated for every website visitor.

The dynamic publishing service 254 allows for reactive publishing offiles that are dynamically altered based on current conditions, userpreferences, and query results, for example. In an online auction housethat has one-hundred items for sale, a dynamic document may be createdin response to a user query. For example, while one-hundred items may beoffered, the user (an avid World War II buff) may only be interested inthose items that relate to World War II. Therefore, the user would entertheir search criteria and a dynamic document would be generated thatincludes fourteen items, each of which is related to World War II. Thisdynamically generated list, which itemizes the fourteen items, may alsospecify the starting bid, the current bid, and the auction ending timefor each item. By generating this document with dynamic publishingservices 254, documents can be generated that more accurately reflectcurrent conditions.

Regardless of whether the static publishing service 252 or dynamicpublishing service 254 produce the file, the file can be published overvarious channels, such as: a web site; an email broadcast; a wirelessbroadcast; a syndication stream; and a printed publication, for example.The file can also be published in various formats, such as HTML, XML,and PDF, for example.

For web site publishing, the file being published may be posted to awebsite so that the file is accessible by various users and guests. Ifsecurity or access is a concern, the file may be published on anintranet (which is not remotely accessible), or within a restrictedaccess user section of a website.

For email broadcasts, the file can be published as an attachment to anemail that is sent out to a distribution list of individual users.Alternatively, the file may be converted into a format (e.g., ASCIItext, and HTML) that is easily incorporated into the body of an email.

For wireless broadcasts, the file can be transmitted to users over awireless network. This file may be text-based (such as an emailattachment sent to a wireless email device) or multimedia-based (such asa sound file sent to a cellular telephone).

For syndication streams, the file may be published on data streams thatare text-based (such as streaming messages), audio-based (such asstreaming audio), video-based (such as streaming video), ormultimedia-based (such as streaming audio/video), for example.

For printed publications, the file being published may be printed ontraditional printing systems (laser printers) and distributed usingtraditional distribution paths (e.g., interoffice mail, courier, or thepostal service, for example).

As above, the dependent applications 12, 14, 16 (FIG. 1) described aboveaccess each service offered by multi-channel deployment group 250 (e.g.,static publishing service 252, and dynamic publishing service 254) bymaking the appropriate request of and establishing a connection throughthe API assigned to that particular service. For this particular group,API 256 is assigned to the static publishing service 252, and API 258 isassigned to the dynamic publishing service 254.

Referring to FIG. 6, a distributed computing system 300 is shown whichincorporates the adaptive content platform described above. Distributedcomputing system 300 includes a local (or first) computing device 302that executes one or more content-enabled dependent applications 12, 14.As described above, each of the dependent applications includes businesslogic and a user interface (FIG. 1).

A storage device 304 stores the individual instruction sets andsubroutines of dependent applications 12, 14. Storage devices 304 may bea hard disk drive, a tape drive, an optical drive, a RAID array, arandom access memory (RAM), or a read-only memory (ROM), for example.Local computing device 302 includes at least one processing unit (notshown) and main memory system (not shown).

A remote (or second) computing device 306 (e.g., a web server) executesthe services layer 24, as described above. Typically, services layer 24is interfaced with a software infrastructure (not shown), which isinterfaced with a data layer (not shown), which is interfaced with an OSlayer (not shown).

A storage device 308 stores the individual instruction sets andsubroutines of services layer 24 (and any additional required layers orinfrastructure). Storage device 308 may be a hard disk drive, a tapedrive, an optical drive, a RAID array, a random access memory (RAM), ora read-only memory (ROM), for example. Remote computing device 306includes at least one processing unit (not shown) and main memory system(not shown).

Local computing device 302 and remote computing device 306 areinterconnected with a network 310, such as a LAN (local area network),WAN (wide area network), the Internet, or an intranet, for example.

While the above-described embodiment discusses the deployment of theservices layer on a single second computer, other configurations arepossible, such as those in which each service, or a group of services,is deployed on its own dedicated computer.

While the above-described embodiment describes a local and a remotecomputing device, this is not intended to define the physical locationof either computing device and is merely intended to indicate that thesecond computing device is remote (i.e., separate) from the firstcomputing device.

While the above-described embodiment discusses the use ofcontent-enabled dependent applications, other configurations arepossible, such as data-enabled dependent applications (i.e., thosedesigned to manage data, as opposed to content).

While the above-described embodiment specifies a software infrastructure24 that is an application server, other configurations are possible,such as a general-purpose operating system (e.g. UNIX, Windows 2000) ora special-purpose operating system (e.g. embedded OS, real time OS).

While the above-described embodiment illustrates the availability ofthree services and three dependent applications, the actual number ofservices and dependent applications can be adjusted based on systemrequirements.

Referring to FIG. 7, a distributed computing method 350 is shown. One ormore content-enabled, dependent applications are executed 352 on a localcomputing device. Each dependent application includes a user interfaceand business logic. A services layer, which is interfaced with thedependent applications and a software infrastructure, is executed 354 ona remote computing device. The services layer provides one or moreservices that are usable by the content-enabled, dependent applications.

A data layer, which includes one or more databases, is interfaced 356with the software infrastructure. A unique application programminginterface is assigned 358 to each of the services. Dependentapplications using a specific service make requests through theapplication programming interface assigned to that service.

The first and second computing devices are interconnected 360 with anetwork.

Referring to FIG. 8, a multi-tier software development method 400 isshown. One or more content-enabled, dependent applications are provided402, each of which includes a user interface and business logic. Aservices layer is provided 404, which is interfaced with the one or morecontent-enabled dependent applications and provides one or more servicesthat are usable by the content-enabled, dependent applications. Theservices layer is interfaced 406 with a software infrastructureinterfaced 408 with a data layer. The data layer includes one or moredatabases.

The embodiments described herein are not limited to the embodimentsdescribed above; it may find applicability in any computing orprocessing environment. The embodiments may be implemented in hardware,software, or a combination of the two. For example, the embodiments maybe implemented using circuitry, such as one or more of programmablelogic (e.g., an ASIC), logic gates, a processor, and a memory.

The embodiments may be implemented in computer programs executing onprogrammable computers that each includes a processor and a storagemedium readable by the processor (including volatile and non-volatilememory and/or storage elements). Each such program may be implemented ina high-level procedural or object-oriented programming language tocommunicate with a computer system. However, the programs can beimplemented in assembly or machine language. The language may be acompiled or an interpreted language.

Each computer program may be stored on an article of manufacture, suchas a storage medium (e.g., CD-ROM, hard disk, or magnetic diskette) ordevice (e.g., computer peripheral), that is readable by a general orspecial purpose programmable computer for configuring and operating thecomputer when the storage medium or device is read by the computer toperform the functions of the embodiments. The embodiments may also beimplemented as a machine-readable storage medium, configured with acomputer program, where, upon execution, instructions in the computerprogram cause a machine to operate to perform the functions of theembodiments described above.

The embodiments described above may be used in a variety ofapplications. Although the embodiments are not limited in this respect,the embodiments may be implemented with memory devices inmicrocontrollers, general purpose microprocessors, digital signalprocessors (DSPs), reduced instruction-set computing (RISC), and complexinstruction-set computing (CISC), among other electronic components.

The embodiments described above may also be implemented using integratedcircuit blocks referred to as main memory, cache memory, or other typesof memory that store electronic instructions to be executed by amicroprocessor or store data that may be used in arithmetic operations.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the embodimentsdescribed above.

1. An adaptive content platform that is stored on a storage mediumhaving a multi-tiered software architecture, comprising: a serviceslayer that includes at least repository services, workflow services,file handling services, and publishing services; a data layer forproviding data services to the adaptive content platform with such dataservices including at least access to database storage and file storagethat contain content; an application server layer that connects to adependent applications layer through the services layer and retrievescontent from the data layer, with the application server layer forhandling operations of the dependent applications within the adaptivecontent platform; the dependent applications layer that includes aplurality of content-enabled dependent applications that connect to theservices layer and a web layer, and whose operations are controlled bythe application server layer, with each content-enabled dependentapplication being capable of being interfaced with services of theservices layer such that specific content from the services layer iscombined to define and build a combination application that emulates astandalone independent application; and the web layer that connects tothe dependent applications layer for enabling users to interface withthe adaptive content platform.
 2. The adaptive content platform of claim1, wherein the services layer includes a unique application programminginterface for each of the services, wherein the content-enableddependent applications using a specific service may make requeststhrough the unique application programming interface assigned to thatservice.
 3. The adaptive content platform of claim 1, wherein therepository services include being part of content management servicesfor storing and managing files, with the content management servicesfurther including search services.
 4. The adaptive content platform ofclaim 3, wherein the repository service includes being used for storingfiles.
 5. The adaptive content platform of claim 4, wherein the searchservice includes being used for allowing users to search files stored bythe repository services.
 6. The adaptive content platform of claim 1,wherein the workflow services include being part of workflow andcollaboration services for managing projects and users, with theworkflow and collaboration services further including collaborationservices.
 7. The adaptive content platform of claim 6, wherein theworkflow and collaboration services includes workflow services formanaging the workflow of files.
 8. The adaptive content platform ofclaim 6, wherein the workflow and collaboration services include usermanagement and authentication services for managing users and usergroups.
 9. The adaptive content platform of claim 6, wherein theworkflow and collaboration services include events and notificationservices for managing and broadcasting notifications to users that weregenerated by one or more services.
 10. The adaptive content platform ofclaim 1, wherein the file handling services includes multi-modal contentcreation services for manual creation and automated importation andconversion of files.
 11. The adaptive content platform of claim 10,wherein the multi-modal content creation services include transformationand content services for converting the formats of files.
 12. Theadaptive content platform of claim 10, wherein the multi-modal contentcreation services include desktop integration services for manualcontribution of content.
 13. The adaptive content platform of claim 10,wherein the multi-modal content creation services include-importservices for facilitating file importation from external systems. 14.The adaptive content platform of claim 1, wherein publishing servicesinclude multi-channel deployment services for publishing files.
 15. Theadaptive content platform of claim 14, wherein the multi-channeldeployment services include publishing services for publishing files toone or more publishing channels.
 16. The adaptive content platform ofclaim 15, wherein the one or more publishing channels includes a website.
 17. The adaptive content platform of claim 15, wherein the one ormore publishing channels includes an email broadcast.
 18. The adaptivecontent platform of claim 15, wherein the one or more publishingchannels includes a wireless broadcast.
 19. The adaptive contentplatform of claim 15, wherein the one or more publishing channelsincludes a syndication stream.
 20. The adaptive content platform ofclaim 15, wherein the one or more publishing channels includes a printedpublication.
 21. The adaptive content platform of claim 14, wherein themulti-channel deployment services include dynamic publishing services.22. The adaptive content platform of claim 14, wherein the multi-channeldeployment services include static publishing services.
 23. The adaptivecontent platform of claim 1, data layer that is interfaced with theapplication server, with the data layer including one or more databases.24. A multi-tiered software architecture that is stored on a storagemedium, comprising: a services layer that includes at least repositoryservices, with the repository services being capable of connection todatabase and file storage that contain content for the adaptive contentplatform; a dependent applications layer that includes a plurality ofcontent-enabled dependent applications that connect to the serviceslayer, with each content-enabled dependent application being capable ofbeing interfaced with the repository services of the services layer suchthat specific content from at least the repository services is combinedto define and build a combination application that emulates a standaloneindependent application; and a web layer that connects to the dependentapplications layer for enabling users to interface with the adaptivecontent-platform.
 25. The adaptive content platform of claim 24, whereinthe services layer includes a plurality of services including at leastrepository services, workflow services, file handling services, andpublishing services.
 26. The adaptive content platform of claim 25,wherein the services layer includes a unique application programminginterface for each of the services through which dependent applicationsusing a specific service make requests.
 27. The adaptive contentplatform of claim 25, wherein the repository services include being partof content management services for storing and managing files, with thecontent management services further including searching services. 28.The adaptive content platform of claim 25, wherein the store theservices store the workflow and collaboration services for managingprojects and users, with the workflow and collaboration services furtherincluding collaboration services.
 29. The adaptive content platform ofclaim 25, wherein the file store the include multi-modal contentcreation services for automated importation and conversion of files. 30.The adaptive content platform of claim 25, wherein the publishingservices include multi-channel deployment services for publishing filesto one or more publishing channels.
 31. The adaptive content platform ofclaim 30, wherein the one or more publishing channels includes a website.
 32. The adaptive content platform of claim 30, wherein the one ormore publishing channels includes an email broadcast.
 33. The adaptivecontent platform of claim 30, wherein the one or more publishingchannels includes a wireless broadcast.
 34. The adaptive contentplatform of claim 30, wherein the one or more publishing channelsincludes a syndication stream.
 35. The adaptive content platform ofclaim 30, wherein the one or more publishing channels includes a printedpublication.
 36. The adaptive content platform of claim 24, furthercomprising an application server layer that connects to the dependentapplications layer through the services layer and retrieves content froma data layer that includes the database and file storage, with theapplications server layer for handling operations of the content-enableddependent applications within the content platform; and the data layerthat is interfaced with the software infrastructure and applicationserver layer, with the data layer including one or more databases. 37.An adaptive content platform that is stored on a storage medium having amulti-tiered software architecture, comprising: an application serverthat connects to a plurality of content-enabled dependent applicationsthrough a services layer and retrieving content from a data layer, withthe applications server for handling operations of the content-enableddependent applications within the content platform; the plurality ofdependent applications, with each content-enabled dependent applicationbeing capable of being interfaced with services of the services layersuch that specific content from the services layer is combined to defineand build a combination application that emulates a standaloneindependent application; the services layer that includes at leastrepository services, with the services layer connecting to a pluralityof content-enabled dependent applications and the application server,and with the repository services being capable of interfacing with eachof the content-enabled dependent applications such that specific contentfrom at least the repository services is combined to define and buildthe combination application that emulates a standalone independentapplication.
 38. The adaptive content platform of claim 37, wherein theservices layer includes a plurality of services including at leastrepository services, workflow services, file handling services, andpublishing services, with each service including a unique applicationprogramming interface through which content-enabled dependentapplications using a specific service make requests.
 39. The adaptivecontent platform of claim 38, further comprising a data layer thatconnects to the application server, with the data layer including one ormore databases.
 40. A distributed computing system, comprising: a firstcomputing device for executing a plurality of content-enabled dependentapplications, with each content-enabled dependent application beingcapable of being interfaced with services of a services layer; and asecond computing device connecting to the first computing device forexecuting a services layer that includes at least repository services,with the services layer connecting to the content-enabled dependentapplications and an application server, and with the repository servicesbeing capable of interfacing with each of the content-enabled dependentapplications such that specific content from at least the repositoryservices is combined to define and build a combination application thatemulates a standalone independent application, the application serverfor handling operations of the content-enabled dependent applicationswithin the distributed computing system and retrieving content from adata layer, and the data layer for containing content that connects tothe application server.
 41. The distributed computing system of claim40, wherein the services layer includes a plurality of servicesincluding at least repository services, workflow services, file handlingservices, and publishing services.
 42. The distributed computing systemof claim 41, wherein the data layer including one or more databases. 43.The distributed computing system of claim 41, wherein the services layerincludes a unique application programming interface for each of theservices through which content-enabled dependent applications using aspecific service make requests.
 44. The distributed computing system ofclaim 40, further comprising a network for interconnecting the first andsecond computing devices.
 45. The distributed computing system of claim44, wherein the network is a local area network.
 46. The distributedcomputing system of claim 44, wherein the network is the Internet. 47.The distributed computing system of claim 44, wherein the network is anintranet.
 48. The distributed computing system of claim 40, wherein thesecond computing device is a web server.
 49. A distributed computingsystem, comprising: a local computing device for executing a pluralityof content-enabled dependent applications, with each content-enableddependent application being capable of being interfaced with services ofa services layer; and a remote computing device connecting to the localcomputing device for executing the services layer that includes at leastrepository services, with the services layer connecting to thecontent-enabled dependent applications and an application server, andwith the repository services being capable of interfacing with each ofthe content-enabled dependent applications such that specific contentfrom at least the repository services is combined to define and build acombination application that emulates a standalone independentapplication, the application server for handling operations of thecontent-enabled dependent applications with the distributed computingsystem and retrieving content from a data layer, and the data layer forcontaining content that connects to the application server.
 50. Thedistributed computing system of claim 49, wherein the services layerincludes a plurality of services including at least repository services,workflow services, file handling services, and publishing services. 51.The distributed computing system of claim 50, wherein the data layerincluding one or more databases.
 52. The distributed computing system ofclaim 50, wherein the services layer includes a unique applicationprogramming interface for each of the services through whichcontent-enabled dependent applications using a specific service makerequests.
 53. The distributed computing system of claim 49, furthercomprising a network for interconnecting the local and remote computingdevices.
 54. The distributed computing system of claim 53, wherein thenetwork is a local area network.
 55. The distributed computing system ofclaim 53, wherein the network is the Internet.
 56. The distributedcomputing system of claim 53 to wherein the network is an intranet. 57.The distributed computing system of claim 53, wherein the remotecomputing device is a web server.
 58. A distributed computing method,comprising the steps of: executing, on a local computing device, aplurality of content-enabled; dependent applications, with eachcontent-enabled dependent application being capable of being interfacedwith services of a services layer; and executing, on a remote computingdevice, a services layer that includes at least repository services,with the services layer connecting to the content-enabled dependentapplications and an application server, with the repository servicesbeing capable of interfacing with each of the content-enabled dependentapplications such that specific content from at least repositoryservices is combined to define and build a combination application soeach content-enabled dependent application will execute as a standaloneindependent application, an application server for handling operationsof the content-enabled dependent applications within the distributedcomputing system and retrieving content from a data layer, and the datalayer for containing content that connects to the application server.59. The distributed computing method of claim 58, wherein the serviceslayer includes a plurality of services including at least repositoryservices, workflow services, file handling services, and publishingservices.
 60. The distributed computing method of claim 59, wherein thedata layer including one or more databases.
 61. The distributedcomputing method of claim 59, further comprising assigning a uniqueapplication programming interface to each of the services through whicheach content-enabled dependent applications using a specific servicemake requests.
 62. The distributed computing method of claim 58, furthercomprising interconnecting the first and second computing devices with anetwork.
 63. The distributed computing method of claim 62, wherein thenetwork is a local area network.
 64. The distributed computing method ofclaim 62, wherein the network is the Internet.
 65. The distributedcomputing method of claim 62, wherein the network is an intranet. 66.The distributed computing method of claim 62, wherein the remotecomputing device is a web server.
 67. A multi-tier software deploymentmethod, comprising the steps of: providing a services layer thatincludes at least repository services, with the repository servicesbeing capable of connection to database and file storage containingcontent; providing a plurality of content-enabled dependent applicationsthat connect to the services layer, with each content-enabled dependentapplication being interfaced with the repository services of theservices layer such that specific content from at least the repositoryservices is combined to define and build a combination application sothat the content-enabled dependent application will execute as astandalone independent application.
 68. The multi-tier softwaredeployment method of claim 67, further comprising interfacing theservices layer with an application server, with the application serverfor handling operations of the content-enabled dependent applicationswithin the distributed computing system and retrieving content from adata layer, and the data layer containing content that connects to theapplication server.
 69. The multi-tier software deployment method ofclaim 68, wherein the data layer including one or more databases.
 70. Acomputer program product residing on a computer readable medium having aplurality of instructions stored thereon which, when executed by aprocessor, cause that processor to: execute, on a local computingdevice, a plurality of content-enabled, dependent applications, witheach content-enabled dependent application being capable of beinginterfaced with services of a services layer; and execute, on a remotecomputing device, a services layer that includes at least repositoryservices, with the services layer connecting to the content-enableddependent applications and an application server, with the repositoryservices being capable of interfacing with each of the content-enableddependent applications such that specific content from at least therepository services is combined to define and build a combinationapplication so each content-enabled dependent application will executeas a standalone independent application, the application server forhandling operations of the content-enabled dependent applications withinthe distributed computing system and retrieving content from a datalayer, and the data layer for containing content that connects to theapplication server.
 71. The computer program product of claim 70,wherein the services layer includes a plurality of services including atleast repository services, workflow services, file handling services,and publishing services.
 72. The computer program product of claim 71,wherein the data layer including one or more databases.
 73. The computerprogram product of claim 70, further comprising instructions to assign aunique application programming interface to each of the services throughwhich content-enabled dependent applications using a specific servicemake requests.
 74. A computer-based, enterprise level system thatincludes an adaptive content platform having a multi-tiered softwarearchitecture, comprising: a services layer for providing enterprise-wideservices that includes at least repository services the, workflowservices, file handling services, and publishing services; anenterprise-wide data layer for providing data services to the adaptivecontent platform with such data services including at least access todatabase storage and file storage that contain content; anenterprise-wide application server layer that connects to a dependentapplications layer through the services layer and retrieves content fromthe data layer, with the application server layer for handlingoperations of the dependent applications within the adaptive contentplatform; the dependent applications layer that includes a plurality ofcontent-enabled dependent applications that connect to the serviceslayer and a web layer, and whose operations are controlled by theapplication server layer, with each content-enabled dependentapplication being capable of being interfaced with enterprise-wideservices of the services layer such that specific content from theenterprise-wide services is combined to define and build a combinationapplication that emulates a standalone independent application; and theweb layer that connects to the dependent applications layer for enablingusers to interface with the adaptive content platform.
 75. Thecomputer-based, enterprise level system of claim 74, wherein theenterprise-wide services layer includes a unique application programminginterface for each of the services, wherein the content-enableddependent applications using a specific service may make requeststhrough the unique application programming interface assigned to thatservice.
 76. The computer-based, enterprise level system of claim 74,wherein the repository services include being part of content managementservices for storing and managing files, with the content managementservices further including search services.
 77. The computer-based,enterprise level system of claim 76, wherein the repository serviceincludes being used for storing files.
 78. The computer-based,enterprise level system of claim 77, wherein search services includebeing used for allowing users to search files stored by the repositoryservices.
 79. The computer-based, enterprise level system of claim 74,wherein the workflow services include being part of workflow andcollaboration services for managing projects and users, with theworkflow and collaboration services further including collaborationservices.
 80. The computer-based, enterprise level system of claim 79,wherein the workflow and collaboration services includes workflowservices for managing the workflow of files.
 81. The computer-based,enterprise level system of claim 79, wherein the workflow andcollaboration services includes user management and authenticationservices for managing users and user groups.
 82. The computer-based,enterprise level system of claim 79, wherein the workflow andcollaboration services include events and notification service formanaging and broadcasting notifications to users that were generated byone or more services.
 83. The computer-based, enterprise level system ofclaim 74, wherein the file handling services includes multi-modalcontent creation services for manual creation and automated importationand conversion of files.
 84. The computer-based, enterprise level systemof claim 83, wherein the multi-modal content creation services includetransformation and content services for converting the formats of files.85. The computer-based, enterprise level system of claim 83, wherein themulti-modal content creation services include desktop integrationservices for manual contribution of content.
 86. The computer-based,enterprise level system of claim 83, wherein the multi-modal contentcreation services include import services for facilitating fileimportation from external systems.
 87. The computer-based, enterpriselevel system of claim 74, wherein the publishing services includemulti-channel deployment services for publishing files.
 88. Thecomputer-based, enterprise level system of claim 87, wherein themulti-channel deployment services include publishing services forpublishing files to one or more publishing channels.
 89. Thecomputer-based, enterprise level system of claim 88, wherein the one ormore publishing channels includes a web site.
 90. The computer-based,enterprise level system of claim 88, wherein the one or more publishingchannels includes an email broadcast.
 91. The computer-based, enterpriselevel system of claim 88, wherein the one or more publishing channelsincludes a wireless broadcast.
 92. The computer-based, enterprise levelsystem of claim 88, wherein the one or more publishing channels includesa syndication stream.
 93. The computer-based, enterprise level system ofclaim 88, wherein the one or more publishing channels includes a printedpublication.
 94. The computer-based, enterprise level system of claim87, wherein the multi-channel deployment services include dynamicpublishing services.
 95. The computer-based, enterprise level system ofclaim 87, wherein the multi-channel deployment services include staticpublishing services.
 96. The computer-based, enterprise level system ofclaim 74, data layer that is interfaced with the application server,with the data layer including one or more databases.
 97. Acomputer-based, enterprise level system that includes an adaptivecontent platform having a multi-tiered software architecture,comprising: a services layer for providing enterprise-wide services thatincludes at least repository services, with the repository servicesbeing capable of connection to database and file storage that containcontent for the adaptive content platform; a dependent applicationslayer that includes a plurality of content-enabled dependentapplications that connect to the services layer, with eachcontent-enabled dependent application being capable of being interfacedwith the repository services of the services layer such that specificcontent from at least the repository services is combined to define andbuild a combination application that emulates a standalone independentapplication; and a web layer that connects to the dependent applicationslayer for enabling users to interface with the adaptive contentplatform.
 98. The computer-based, enterprise level system of claim 97,wherein the services layer includes a plurality of services including atleast repository services, workflow services, file handling services,and publishing services.
 99. The computer-based, enterprise level systemof claim 98, wherein the services layer includes a unique applicationprogramming interface for each of the services through which dependentapplications using a specific service make requests.
 100. Thecomputer-based, enterprise level system of claim 98, wherein therepository services include being part of content management servicesfor storing and managing files, with the content management servicesfurther including searching services.
 101. The computer-based,enterprise level system of claim 98, wherein the workflow servicesinclude being part of workflow and collaboration services for managingprojects and users, with the workflow and collaboration services furtherincluding collaboration services.
 102. The computer-based, enterpriselevel system of claim 98, wherein the file handling services includemulti-modal content creation services for automated importation andconversion of files.
 103. The computer-based, enterprise level system ofclaim 98, wherein the publishing services include multi-channeldeployment services for publishing files to one or more publishingchannels.
 104. The computer-based, enterprise level system of claim 103,wherein the one or more publishing channels includes a web site. 105.The computer-based, enterprise level system of claim 103, wherein theone or more publishing channels includes an email broadcast.
 106. Thecomputer-based, enterprise level system of claim 103, wherein the one ormore publishing channels includes a wireless broadcast.
 107. Thecomputer-based, enterprise level system of claim 103, wherein the one ormore publishing channels includes a syndication stream.
 108. Thecomputer-based, enterprise level system of claim 103, wherein the one ormore publishing channels includes a printed publication.
 109. Thecomputer-based, enterprise level system of claim 97, further comprisingan enterprise-wide application server layer that connects to thedependent applications layer through the services layer and retrievescontent from an enterprise-wide data layer that include the database andfile storage, with the applications server layer for handling operationsof the content-enabled dependent applications within the contentplatform; and the enterprise-wide data layer that is interfaced with thesoftware infrastructure and application server layer, with the datalayer including one or more databases.
 110. A computer-based, enterpriselevel system that includes an adaptive content platform having amulti-tiered software architecture, comprising: an enterprise-wideapplication server that connects to a plurality of content-enableddependent applications through a services layer and retrieve contentfrom a data layer, with the applications server for handling operationsof the content-enabled dependent applications within the contentplatform; the plurality of dependent applications, with eachcontent-enabled dependent application being capable of being interfacedwith services of the services layer such that specific content from theservices layer is combined to define and build a combination applicationthat emulates a standalone independent application; and the serviceslayer for providing enterprise-wide services that includes at leastrepository services, with the services layer connecting to a pluralityof content-enabled dependent applications and the application server,and with the repository services being capable of interfacing with theeach of the dependent applications such that specific content from atleast the repository services is combined to define and build thecombination application that emulates a standalone independentapplication.
 111. The computer-based, enterprise level system of claim110, wherein the services layer includes a plurality of servicesincluding at least repository services, workflow services, file handlingservices, and publishing services, with each service including a uniqueapplication programming interface through which content-enableddependent applications using a specific service make.
 112. Thecomputer-based, enterprise level system of claim 111, further comprisingan enterprise-wide data layer that connects to the application server,with the data layer including one or more databases.
 113. Anenterprise-wide, distributed computing system, comprising: a firstcomputing device for executing a plurality of content-enabled dependentapplications, with each content-enabled dependent application beingcapable of being interfaced with services of a services layer; and asecond computing device connecting to the first computing device forexecuting a services layer for providing enterprise-wide services thatincludes at least repository services, with the services layerconnecting to the content-enabled dependent applications and anenterprise-wide application server, and with the repository servicesbeing capable of interfacing with each of the content-enabled dependentapplications such that specific content for at least the repositoryservices is combined to define and build a combination application thatemulates a standalone independent application, the application serverfor handling operations of the content-enabled dependent applicationswithin the distributed computing system and retrieving content for adata layer, and the data layer containing content that connects to theapplication server.
 114. The enterprise-wide, distributed computingsystem of claim 113, wherein the services layer includes a plurality ofservices including at least repository services, workflow services, filehandling services, and publishing services.
 115. The enterprise-wide,distributed computing system of claim 114, where the data layerincluding one or more databases.
 116. The enterprise-wide, distributedcomputing system of claim 114, wherein the services layer includes aunique application programming interface for each of the servicesthrough which content-enabled dependent applications using a specificservice make requests.
 117. The enterprise-wide, distributed computingsystem of claim 113, further comprising a network for interconnectingthe first and second computing devices.
 118. The enterprise-wide,distributed computing system of claim 117, wherein the network is alocal area network.
 119. The enterprise-wide, distributed computingsystem of claim 117, wherein the network is the Internet.
 120. Theenterprise-wide, distributed computing system of claim 117, wherein thenetwork is an intranet.
 121. The enterprise-wide, distributed computingsystem of claim 113, wherein the second computing device is a webserver.
 122. An enterprise-wide, distributed computing system,comprising: a local computing device for executing a plurality ofcontent-enabled dependent applications, with each content-enableddependent application being capable of interfaced with services of aservices layer; and a remote computing device connecting to the localcomputing device for executing the services layer for providingenterprise-wide services that includes at least repository services,with the services layer connecting to the content-enabled dependentapplications and an enterprise-wide application server, and with therepository services being capable of interfacing with each of thecontent-enabled dependent applications such that specific content fromat least the repository services is combined to define and build acombination application that emulates a standalone independentapplication, the application server for handling operations of thecontent-enabled dependent applications with the distributed computingsystem and retrieving content from a data layer, and the data layer forcontaining content that connects to the application server.
 123. Theenterprise-wide, distributed computing system of claim 122, wherein theservices layer includes a plurality of services including at leastrepository services, workflow services, file handling services, andpublishing services.
 124. The enterprise-wide, distributed computingsystem of claim 123, wherein the data layer including one or moredatabases.
 125. The enterprise-wide, distributed computing system ofclaim 123, wherein the services layer includes a unique applicationprogramming interface for each of the services through whichcontent-enabled dependent applications using a specific service makerequests.
 126. The enterprise-wide, distributed computing system ofclaim 122, further comprising a network for interconnecting the localand remote computing devices.
 127. The enterprise-wide, distributedcomputing system of claim 126, wherein the network is a local areanetwork.
 128. The enterprise-wide, distributed computing system of claim126, wherein the network is the Internet.
 129. The enterprise-wide,distributed computing system of claim 126, wherein the network is anintranet.
 130. The enterprise-wide, distributed computing system ofclaim 126, wherein the remote computing device is a web server.
 131. Anenterprise-wide, distributed computing method, comprising the steps of:executing, on a local computing device, a plurality of content-enabled,dependent applications, with each content-enabled dependent applicationbeing capable of being interfaced with services of a services layer; andexecuting, on a remote computing device, a services layer for providingenterprise-wide services that includes at least repository services,with the services layer connecting to the content-enabled dependentapplications and an application server, with the repository servicesbeing capable of interfacing with each of the content-enabled dependentapplications such that specific content from at least the repositoryservices is combined to define and build a combination application soeach content-enabled dependent application will execute as a standaloneindependent application, an enterprise-wide application server forhandling operations of the content-enabled dependent applications withinthe distributed computing system and retrieving content from a datalayer, and the data layer containing content that connects to theapplication server.
 132. The enterprise-wide, distributed computingmethod of claim 131, wherein the services layer includes a plurality ofservices including at least repository services, workflow services, filehandling services, and publishing services.
 133. The enterprise-wide,distributed computing method of claim 132, wherein the data layerincluding one or more databases.
 134. The enterprise-wide, distributedcomputing method of claim 132, further comprising assigning a uniqueapplication programming interface to each of the services through whicheach content-enabled dependent applications using a specific servicemake requests.
 135. The enterprise-wide, distributed computing method ofclaim 131, further comprising interconnecting the first and secondcomputing devices with a network.
 136. The enterprise-wide, distributedcomputing method of claim 135, wherein the network is a local areanetwork.
 137. The enterprise-wide, distributed computing method of claim135, wherein the network is the Internet.
 138. The enterprise-wide,distributed computing method of claim 135, wherein the network is anintranet.
 139. The enterprise-wide, distributed computing method ofclaim 135, wherein the remote computing device is a web server.
 140. Adeployment method for a computer-based, enterprise level system thatincludes multi-tier software, comprising the steps of: providing aservices layer for providing enterprise-wide services that includes atleast repository services, with the repository services being capable ofconnection to database and file storage containing content; provide aplurality of content-enabled, dependent applications that connect to theservices layer, with each content-enabled dependent application beinginterfaced with the repository services of the services layer such thatspecific content from at least the repository services is combined todefine and build a combination application so that the content-enableddependent application will execute as a standalone independent.
 141. Themethod of claim 140, further comprising interfacing the services layerwith an enterprise-wide application server, with the application serverfor handling operations of the content-enabled dependent applicationswithin the distributed computing system and retrieving content for adata layer, and the data layer containing content that connects to theapplication server.
 142. The method of claim 141, wherein the data layerincluding one or more databases.
 143. An enterprise-wide, computer-basedsystem with a computer program product residing on a computer readablemedium having a plurality of instructions stored thereon which, whenexecuted by the processor, cause that processor to: execute, on a localcomputing device, a plurality of content-enabled, dependentapplications, with each content-enabled dependent application beingcapable of being interfaced with services layer; and execute, on aremote computing device, an enterprise-wide services layer that includesat least repository services, with the services layer connecting to thecontent-enabled dependent applications and an enterprise-wideapplication server, with the repository services being capable ofinterfacing with each of the content-enabled dependent applications suchthat specific content from at least the repository services is combinedto define and build a combination application so each content-enableddependent application will execute as a standalone independentapplication, the application server for handling operations of thecontent-enabled dependent applications within the distributed computingsystem and retrieving content for a data layer, and the data layer forcontaining content that connects to the application server.
 144. Thesystem of claim 143, wherein the services layer includes a plurality ofservices including at least repository services, workflow services, filehandling services, and publishing services.
 145. The system of claim 14,wherein the data layer including one or more databases.
 146. The systemof claim 143, further comprising instructions to assign a uniqueapplication programming interface to each of the services through whichcontent-enabled dependent applications using a specific service makerequests.